home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Software Vault: The Gold Collection
/
Software Vault - The Gold Collection (American Databankers) (1993).ISO
/
cdr25
/
com2207.zip
/
COMBETA.DOC
< prev
next >
Wrap
Text File
|
1993-03-01
|
6KB
|
129 lines
BETA RELEASE OF OS/2 COMMUNICATION DRIVERS
IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESSED OR IMPLIED, INCLUDING
WITHOUT LIMITATION, WARRANTIES OF FITNESS AND MERCHANTABILITY WITH
RESPECT TO THE INFORMATION IN THIS DOCUMENT AND INCLUDED SOFTWARE
PRODUCTS. . BY FURNISHING THISMATERIAL, IBM GRANTS NO LICENSES TO ANY
RELATED PATENTS OR COPYRIGHTS.
Copyright IBM Corporation, 1992, all rights reserved.
1.0 INSTALLATION PROCEDURE
a. The following files will be replaced:
x:\OS2\COM.SYS
x:\OS2\MDOS\VCOM.SYS
x:\OS2\MDOS\WINOS2\SYSTEM\COMM.DRV
These files will be backed up.
b. Switch to the drive where the BETA files are
located.
c. Enter "cominst x:" at the command line where
x: is the drive letter of the OS/2 Partition.
2.0 DESCRIPTION OF DRIVERS
The following is a brief description of the BETA
communication drivers for OS/2 2.0. There are new
parameters for the COM.SYS which is located in the
CONFIG.SYS file.
2.1 COM.SYS
COM.SYS now has new parameters to indicate the COM port
number, the I/O address, the UNIQUE IRQ level, how to
handle spurious interrupts and to indicate the type of
UART chip. An example follows:
DEVICE=C:\OS2\COM.SYS (3,xxxx,ii,s,t) [(4,xxxx,ii,s,t)]
where the last parameter is optional. NOTE: You must
have COM3 defined inorder for COM4 to work. The usual
symptom of a bad I/O address or interrupt is when you
open a DOS or OS/2 command prompt and it fails.
n : COM port number (usually 3 and 4 but it is
possible to configure COM2 to a
differrent IRQ or I/O Address
xxxx : COM port address
ii : IRQ level
s : Spurious interrupt handling switch
values:
D or d to deinstall COM driver if
more than 1000 consecutive
spurious interrupts occur.
I or i to ignore spurious interrupt.
P or p to post error if more than 1000
consecutive interrupts
occur. When post error,
some apps can hang.
t : Type of UART chip.
values:
F or f for FIFO 16550 UART chip.
Other characters will be
treated as non FIFO like
16450 or 8250.
If no parameter is passed,
COM.SYS will check the
UART. This is to support
Western Digital's 16550AF
compatible chip which has a
bug in its FIFO support.
W or w For Western Digital's 16550AF
compatible UART (possible
performance improvement)
COM.SYS also has the following fixes:
1. Change the 0xFF check to see the presence of port in
the given address.
2. Change from DevHlp EOI to writing port 0x20 to
reduce interrupt pass. (Possible performance
improvement)
3. Better checking of FIFO.
4. COM.SYS does not detect Hayes ESP card so that Hayes
ESP card can be used as a regular dual asynch card.
5. New DOS_SETTING Property : HW_COM (will be renamed
to COM_DIRECT_ACCESS later on.). HW_COM removes the
IO hook of VCOM.SYS after check the access control.
If the app only works when VCOM.SYS is not loaded,
HW_COM will help the problem. When HW_COM is on,
any application which requires the presence of
VCOM.SYS will not work in the DOS session. This
VCOM.SYS requires the new COM.SYS.
2.2 VCOM.SYS
No parameters or settings required.
2.3 COMM.DRV
COMM.DRV contains the support for COM3 and COM4 in
WinOS2. This COMM.DRV requires the new VCOM.SYS.